Skip to content

Add swagger changes for zone redundancy property to databases, elastic pools and editions#1813

Merged
fearthecowboy merged 8 commits intoAzure:currentfrom
emgu-ms:swaggerChanges
Oct 18, 2017
Merged

Add swagger changes for zone redundancy property to databases, elastic pools and editions#1813
fearthecowboy merged 8 commits intoAzure:currentfrom
emgu-ms:swaggerChanges

Conversation

@emgu-ms
Copy link
Copy Markdown
Contributor

@emgu-ms emgu-ms commented Oct 6, 2017

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@msftclas
Copy link
Copy Markdown

msftclas commented Oct 6, 2017

CLA assistant check
All CLA requirements met.

Copy link
Copy Markdown
Contributor

@fearthecowboy fearthecowboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emgu-ms -- if you are an MS employee, make sure your account is tied to your domain account so that it's cleared by the CLA check.

if not, you can sign the cla (follow the instructions in the post...)

@jaredmoo
Copy link
Copy Markdown
Contributor

jaredmoo commented Oct 7, 2017

Looks good. Just want to make sure this is on in at least 1 production region and has .NET SDK test written and working on your machine before this gets merged.

@fearthecowboy
Copy link
Copy Markdown
Contributor

@emgu-ms -- ping this thread when you've satisfied @jaredmoo 's conditions.

"description": "Whether or not zone redundancy is supported for the edition.",
"type": "boolean",
"type": "string",
"format": "boolean"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need a comma at the end here

Copy link
Copy Markdown
Contributor

@jaredmoo jaredmoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, please confirm that .NET SDK is working and then let's merge.

@jaredmoo
Copy link
Copy Markdown
Contributor

Oh ho, linter errors. It looks like boolean format doesn't exist. I think you'll have to just remove those format's and treat it as plain string.

@fearthecowboy
Copy link
Copy Markdown
Contributor

Is the value a boolean?

swagger uses "type":"boolean" -- not format

.

@jaredmoo
Copy link
Copy Markdown
Contributor

The value is either "true" or "false" as a string, not true or false as a boolean literal. This is an unfortunate limitation in our API stack that implements api-version 2014-04-01. The later api-versions (which are being deployed soon) will have this as a real boolean.

@fearthecowboy
Copy link
Copy Markdown
Contributor

Ah. ok.

,<

Ouch.

@azuresdkciprbot
Copy link
Copy Markdown

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/sql/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link
Copy Markdown

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/sql/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@fearthecowboy
Copy link
Copy Markdown
Contributor

Hey @emgu-ms,

are we getting close to being ready to merge this?

@emgu-ms
Copy link
Copy Markdown
Contributor Author

emgu-ms commented Oct 17, 2017

Yup! We're good! Thanks all :)

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-node

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants